home *** CD-ROM | disk | FTP | other *** search
- Path: nntp.teleport.com!usenet
- From: curt@teleport.com (Curt...)
- Newsgroups: comp.dcom.modems
- Subject: Re: Windows config?
- Date: Mon, 22 Jan 1996 08:14:00 GMT
- Organization: Teleport - Portland's Public Access (503) 220-1016
- Message-ID: <3103464a.6905423@news.teleport.com>
- References: <4dr2ts$p8c_002@jgreene.cts.com>
- NNTP-Posting-Host: ip-pdx12-01.teleport.com
- X-Newsreader: Forte Agent .99c/16.141
-
- jgreene@cts.com (Jim Greene) wrote:
-
- > I put a Practical Peripherals 14400FXSA internal modem into a 33MHz '386 and
- > tried to run pcAnywhere 4.5 for DOS; it didn't work. I put in another
- > identical modem; it didn't work. I put in a new controller card set; bingo,
- > sort of. Now, the DOS pcAnywhere works fine, but nothing works in Windows,
- > either Terminal or pcAnywhere for Windows. When I quit Windows, the DOS
- > version doesn't work, until I reboot. My guess is that Windows is setting
- > something on the modem, and leaving it that way when I quit Windows.
-
-
- My guess is that your guess is probably right. With each piece of comm software
- you use, be sure to include a modem initiation string which re-initializes your modem
- from scratch. Such a string frequently would start off with the letters AT&F....., which
- loads one of the factory default templates (basically killing any funny settings left
- by the last piece of software).
-
- Good luck...
- Curt...
-
-